Open
Conversation
Contributor
|
I don't understand PackagesProposal... but just by its name I would say that this belongs to Agama, not this repo. Why here? |
Contributor
Author
|
@mvidner that is good question and I already think if this is good place for it. That is also reason why I try to not use agama specific names and make it more generic. In general it is about making application requirements that is not directly set by user, but also not just result of running solver. But I am open to move it elsewhere as code is not rocket science. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Idea is to have in rust part counterpart of Yast::PackagesProposal. So there is now two new structs. One is for capturing requirements and second is for capturing mapping between id and its requirements.